@IljaN - please:

• add respective labels
• assign yourself as being responsible when creating the PR
• add to milestone

On the content - did you check that the behat tests will transform the upload to chunking?

Checking core feature files for webdav - we explicitly chunk: https://github.com/owncloud/core/blob/master/tests/acceptance/features/apiWebdav/webdav-related-new-endpoint.feature#L464-L473

something to consider - instead of uploading a large file, create the file during the test run - so people do not have to check out unecessary large github repositories

also, as discussed in the core PR:

• add a test that does a DELETE on the uploads folder for cancellation, to confirm there is no permission issue

There seems to be no pre-defined step to delete files outside of /$user/files, should i create one? @individual-it, @phil-davis

Maybe an abstraction step for the chunking process should be provided which does the whole process without needing to do it manually like this:

  @mailhog
  Scenario: A guest user can upload chunked files
    Given as user "admin"
    And user "user0" has been created
    And user "admin" has created guest user "guest" with email "[email protected]"
    And the HTTP status code should be "201"
    And user "user0" has created a folder "/tmp"
    And user "user0" has shared folder "/tmp" with user "[email protected]"
    And guest user "guest" has registered
    When user "[email protected]" creates a new chunking upload with id "chunking-42" using the API
    And user "[email protected]" uploads new chunk file "1" with "AAAAA" to id "chunking-42" using the API
    And user "[email protected]" uploads new chunk file "2" with "BBBBB" to id "chunking-42" using the API
    And user "[email protected]" uploads new chunk file "3" with "CCCCC" to id "chunking-42" using the API
    And user "[email protected]" moves new chunk file with id "chunking-42" to "/tmp/myChunkedFile.txt" using the API
    Then as "[email protected]" the file "/tmp/myChunkedFile.txt" should exist
    When user "[email protected]" deletes folder "/uploads/chunking-42" using the API
    Then as "[email protected]" the file "/uploads/chunking-42" should not exist

@PVince81 test added

@IljaN yes, compressing that list of chunking steps would be nice for "routine" chunking tests - it can assume some stuff and do it all. If you want detailed control (upload weird numbers of chunks of different sizes out-of-order,...) then you can write it out as individual steps.
I will make a PR to provide that.
owncloud/core#31616

But for now the long-winded steps work.

@IljaN
restarted - even though it is now green for stable10 - these errors strike me - cc @PVince81

[Fri Jun  1 23:26:28 2018] Storage wrapper 'oc_readonly' was not registered via the 'OC_Filesystem - preSetup' hook which could cause potential problems.
[Fri Jun  1 23:26:28 2018] Could not get node for path: "uploads/[email protected]/chunking-42/.file" : File with name //chunking-42 could not be located

first warning is expected, needs fixing in core at some point.

second one is strange... I'll have a look

hmmm, also something missing on master ? (from Drone results)

--- GuestsContext has missing steps. Define them with these snippets:

    /**
     * @When user :arg1 cancels chunking-upload with id :arg2 using the API
     */
    public function userCancelsChunkingUploadWithIdUsingTheApi($arg1, $arg2)
    {
        throw new PendingException();
}

• requires [master] fix chunked upload for guest app core#31618 for master

@PVince81 - missing master as the required tests step implementation is in core

@patrickjahns I'm not seeing the second error from your comment #212 (comment) when running tests locally. Was it from a specific drone run ?

@patrickjahns ok I see the error on Drone: https://drone.owncloud.com/owncloud/guests/18/43 line 190.

Since Drone runs with the daily tarball I should try with that one locally as well.

@patrickjahns I managed to reproduce this, I wasn't looking properly. Using a search for ".file" helped me find it in the local log.

It's a core issue: owncloud/core#31631

Some of our Sabre plugins is trying to clean up custom properties and tries to get the node after it was already moved, so it doesn't find it. Nothing to worry about in the context of uploads, but I mentioned in the ticket that we should check whether a real issue might exist with regular files and custom properties.

added more verification steps as advised by @phil-davis

master got the acceptance test step so I expect everything to be green on all branches now

Looks good, assuming CI passes.

daily-master-qa... need to wait for tomorrow as it will contain the fix. stay tuned

restarted failed builds, expecting success with today's daily-master-qa